The Juniper router must be configured to enforce approved authorizations for controlling the flow of information within the network based on organization-defined information flow control policies.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-253973	JUEX-RT-000010	SV-253973r843952_rule		Medium

Description
Information flow control regulates where information is allowed to travel within a network and between interconnected networks. The flow of all network traffic must be monitored and controlled so it does not introduce any unacceptable risk to the network infrastructure or data. Information flow control policies and enforcement mechanisms are commonly employed by organizations to control the flow of information between designated sources and destinations (e.g., networks, individuals, and devices) within information systems. Enforcement occurs, for example, in boundary protection devices (e.g., gateways, routers, guards, encrypted tunnels, and firewalls) that employ rule sets or establish configuration settings that restrict information system services, provide a packet filtering capability based on header information, or provide a message filtering capability based on message content (e.g., implementing key word searches or using document characteristics).

Description

Information flow control regulates where information is allowed to travel within a network and between interconnected networks. The flow of all network traffic must be monitored and controlled so it does not introduce any unacceptable risk to the network infrastructure or data. Information flow control policies and enforcement mechanisms are commonly employed by organizations to control the flow of information between designated sources and destinations (e.g., networks, individuals, and devices) within information systems. Enforcement occurs, for example, in boundary protection devices (e.g., gateways, routers, guards, encrypted tunnels, and firewalls) that employ rule sets or establish configuration settings that restrict information system services, provide a packet filtering capability based on header information, or provide a message filtering capability based on message content (e.g., implementing key word searches or using document characteristics).

STIG	Date
Juniper EX Series Switches Router Security Technical Implementation Guide	2024-06-10

Details

Check Text ( C-57425r843950_chk )
This requirement is not applicable for the DODIN Backbone. Review the router configuration to verify that stateless firewall filters are configured to allow or deny traffic for specific source and destination addresses as well as ports and protocols. Verify the IP addresses are appropriate for the target environment. IP addresses are configured in lists at [edit policy-options] or are directly embedded into each term. [edit policy-options] prefix-list inside-addresses-ipv4 { /; /; } prefix-list inside-addresses-ipv6 { /; /; } For example: [edit firewall] family inet { filter authorized-outbound-ipv4 { term permitted-http { from { source-prefix-list { inside-addresses-ipv4; } destination-address { /; } protocol tcp; destination-port http; } then accept; } : : term permitted-source-addresses { from { source-prefix-list { inside-addresses-ipv4; } protocol-except tcp; destination-port-except http; } then accept; } term default-deny { then { log; syslog; discard; } } } } family inet6 { filter authorized-outbound-ipv6 { term permitted-http { from { source-prefix-list { inside-addresses-ipv6; } destination-address { /; } next-header tcp; destination-port http; } then accept; } : : term permitted-source-addresses { from { source-prefix-list { inside-addresses-ipv6; } next-header-except tcp; destination-port-except http; } then accept; } term default-deny { then { log; syslog; discard; } } } } Verify filters are applied to the correct interface. For example, the "authorized-outbound" filter, as written, should be applied to the ingress of internal interfaces: [edit interfaces] { unit { family inet { filter { input authorized-outbound-ipv4; } address /; } family inet6 { filter { input authorized-outbound-ipv6; } address /; } } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" and "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. If the router is not configured to enforce approved authorizations for controlling the flow of information within the network based on organization-defined information flow control policies, this is a finding.

Check Text ( C-57425r843950_chk )

This requirement is not applicable for the DODIN Backbone.

Review the router configuration to verify that stateless firewall filters are configured to allow or deny traffic for specific source and destination addresses as well as ports and protocols. Verify the IP addresses are appropriate for the target environment. IP addresses are configured in lists at [edit policy-options] or are directly embedded into each term.

[edit policy-options]
prefix-list inside-addresses-ipv4 {
/;
/;
}
prefix-list inside-addresses-ipv6 {
/;
/;
}

For example:
[edit firewall]
family inet {
filter authorized-outbound-ipv4 {
term permitted-http {
from {
source-prefix-list {
inside-addresses-ipv4;
}
destination-address {
/;
}
protocol tcp;
destination-port http;
}
then accept;
}
:

:
term permitted-source-addresses {
from {
source-prefix-list {
inside-addresses-ipv4;
}
protocol-except tcp;
destination-port-except http;
}
then accept;
}
term default-deny {
then {
log;
syslog;
discard;
}
}
}
}
family inet6 {
filter authorized-outbound-ipv6 {
term permitted-http {
from {
source-prefix-list {
inside-addresses-ipv6;
}
destination-address {
/;
}
next-header tcp;
destination-port http;
}
then accept;
}
:

:
term permitted-source-addresses {
from {
source-prefix-list {
inside-addresses-ipv6;
}
next-header-except tcp;
destination-port-except http;
}
then accept;
}
term default-deny {
then {
log;
syslog;
discard;
}
}
}
}

Verify filters are applied to the correct interface. For example, the "authorized-outbound" filter, as written, should be applied to the ingress of internal interfaces:
[edit interfaces]
{
unit {
family inet {
filter {
input authorized-outbound-ipv4;
}
address /;
}
family inet6 {
filter {
input authorized-outbound-ipv6;
}
address /;
}
}
}
Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" and "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter.

If the router is not configured to enforce approved authorizations for controlling the flow of information within the network based on organization-defined information flow control policies, this is a finding.

Fix Text (F-57376r843951_fix)
This requirement is not applicable for the DODIN Backbone. Configure stateless firewall filters to allow or deny traffic for specific source and destination addresses as well as ports and protocols. Example prefix-lists: set policy-options prefix-list inside-addresses-ipv4 set policy-options prefix-list inside-addresses-ipv6 Example firewall filter: set firewall family inet filter authorized-outbound-ipv4 term permitted-source-addresses from source-prefix-list inside-addresses-ipv4 set firewall family inet filter authorized-outbound-ipv4 term permitted-source-addresses then accept set firewall family inet filter authorized-outbound-ipv4 term 2 then log set firewall family inet filter authorized-outbound-ipv4 term 2 then syslog set firewall family inet filter authorized-outbound-ipv4 term 2 then discard set firewall family inet6 filter authorized-outbound-ipv6 term permitted-source-addresses from source-prefix-list inside-addresses-ipv6 set firewall family inet6 filter authorized-outbound-ipv6 term permitted-source-addresses then accept set firewall family inet6 filter authorized-outbound-ipv6 term 2 then log set firewall family inet6 filter authorized-outbound-ipv6 term 2 then syslog set firewall family inet6 filter authorized-outbound-ipv6 term 2 then discard Example firewall filter applied to ingress of internal interface: set interfaces unit family inet filter input authorized-outbound-ipv4 set interfaces unit family inet address / set interfaces unit family inet6 filter input authorized-outbound-ipv6 set interfaces unit family inet6 address /

Fix Text (F-57376r843951_fix)

This requirement is not applicable for the DODIN Backbone.

Configure stateless firewall filters to allow or deny traffic for specific source and destination addresses as well as ports and protocols.

Example prefix-lists:
set policy-options prefix-list inside-addresses-ipv4
set policy-options prefix-list inside-addresses-ipv6

Example firewall filter:
set firewall family inet filter authorized-outbound-ipv4 term permitted-source-addresses from source-prefix-list inside-addresses-ipv4
set firewall family inet filter authorized-outbound-ipv4 term permitted-source-addresses then accept
set firewall family inet filter authorized-outbound-ipv4 term 2 then log
set firewall family inet filter authorized-outbound-ipv4 term 2 then syslog
set firewall family inet filter authorized-outbound-ipv4 term 2 then discard

set firewall family inet6 filter authorized-outbound-ipv6 term permitted-source-addresses from source-prefix-list inside-addresses-ipv6
set firewall family inet6 filter authorized-outbound-ipv6 term permitted-source-addresses then accept
set firewall family inet6 filter authorized-outbound-ipv6 term 2 then log
set firewall family inet6 filter authorized-outbound-ipv6 term 2 then syslog
set firewall family inet6 filter authorized-outbound-ipv6 term 2 then discard

Example firewall filter applied to ingress of internal interface:
set interfaces unit family inet filter input authorized-outbound-ipv4
set interfaces unit family inet address /
set interfaces unit family inet6 filter input authorized-outbound-ipv6
set interfaces unit family inet6 address /